fix: fixed and improved docker build and runtime configs #2024
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Fixed Docker stage name mismatches across all files (runtime/development) - Restructured Dockerfile with proper Railway deployment support - Added missing ARG declarations and aligned pnpm versions - Updated port configurations from 3000 to 5173 - Cleaned docker-compose.yaml profiles - Added Railway-specific deployment options
- Updated railway Docker stage to include Wrangler dependencies - Added --local flag to disable host checking in production - Added DANGEROUSLY_DISABLE_HOST_CHECK env var for Railway - Fixed vite server configuration for deployment environments
- Removed railway Docker stage - Removed start:railway and dockerbuild:railway scripts - Reverted vite.config.ts server settings - Cleaned up for Cloudflare Pages deployment only
mouradamri21
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the Docker build and runtime configuration to improve clarity, consistency, and compatibility, especially for local development and deployment environments. The changes standardize Docker build targets, update documentation and scripts, and refine the Dockerfile for better runtime behavior and support for development tools.
Docker build and runtime improvements:
Standardized Docker build targets by renaming
bolt-ai-productiontoruntimeandbolt-ai-developmenttodevelopmentacrossDockerfile,docker-compose.yaml, build scripts, and documentation. This unifies naming and reduces confusion when building or running containers. [1] [2] [3] [4] [5] [6] [7] [8]Updated the runtime Docker image to:
5173instead of3000for consistency with development and deployment environments.bindings.sh,wrangler.toml,functions,worker-configuration.d.ts) needed forwrangler pages dev.bindings.shexecutable and ensurepnpmis enabled in the runtime stage.5173).pnpm run dockerstartfor local development withwrangler pages dev.Documentation and script updates:
CONTRIBUTING.md,docs/docs/CONTRIBUTING.md) and build scripts (package.json) to use the new Docker build target names (runtime,development). [1] [2] [3] [4] [5]Dependency and configuration changes:
pnpmversion from9.15.9to9.14.4in the Dockerfile for both build and runtime stages, possibly for compatibility reasons. [1] [2]AWS_BEDROCK_CONFIGas a build argument in the Dockerfile to support additional configuration.Minor build and script fixes:
package.jsonto use the correct config file extension (vite-electron.config.ts).Environment and compose file cleanup:
COMPOSE_PROFILES=productionand related comments fromdocker-compose.yamlto streamline environment configuration.Co-author: Factory AI droid agents